|
Dynamic systems development method (DSDM) is an agile project delivery framework, primarily used as a software development method.〔Keith Richards, ''Agile project management: running PRINCE2 projects with DSDM Atern.'' OGC - Office of Government Commerce. The Stationery Office, 31 jul. 2007.〕〔Plonka, Laura, et al. "UX Design in Agile: A DSDM Case Study." ''Agile Processes in Software Engineering and Extreme Programming.'' Springer International Publishing, 2014. 1-15.〕 First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method.〔Abrahamsson, Pekka, et al. "(New directions on agile methods: a comparative analysis )." Software Engineering, 2003. Proceedings. 25th International Conference on. Ieee, 2003.〕 In 2007 DSDM became a generic approach to project management and solution delivery. DSDM is an iterative and incremental approach that embraces principles of Agile development, including continuous user/customer involvement. DSDM fixes cost, quality and time at the outset and uses the MoSCoW prioritisation of scope into ''musts'', ''shoulds'', ''coulds'' and ''won't haves'' to adjust the project deliverable to meet the stated time constraint. DSDM is one of a number of Agile methods for developing software and non-IT solutions, and it forms a part of the Agile Alliance. In 2007, DSDM was rebranded 'DSDM Atern'.〔Richards, Keith. Agile project management: running PRINCE2 projects with DSDM Atern. The Stationery Office, 2007.〕〔DSDM Consortium. "DSDM Atern: the Handbook." DSDM Consortium (2008).〕 The name Atern was a shortening of Arctic tern - a collaborative bird that can travel vast distances and epitomises many facets of the method which are natural ways of working e.g. prioritisation and collaboration. In 2014, DSDM dropped the branding 'Atern' and reverted to its original name in the latest version of the method in the 'DSDM Agile Project Framework' positioned as "an ideal wrapper for more limited Agile frameworks... DSDM is often used to provide the full 'project' focus to compliment Scrum's team focussed product development process.". At the same time the new DSDM manual recognised the need to operate alongside other frameworks for service delivery (esp. ITIL) PRINCE2, Managing Successful Programmes, and PMI-BOK.〔The DSDM Agile Project Framework manual, 2014 pages 4, 16〕 In addition DSDM can be easily accommodated as part of wider agile management approaches. The previous version (DSDM 4.2) had only contained guidance on how to use DSDM with Extreme Programming. == DSDM and the DSDM Consortium: origins == In the early 1990s, rapid application development (RAD) was spreading across the IT industry. The user interfaces for software applications were moving from the old green screens to the graphical user interfaces that are used today. New application development tools were coming on the market, such as PowerBuilder. These enabled developers to share their proposed solutions much more easily with their customers – prototyping became a reality and the frustrations of the classical, sequential (waterfall) development methods could be put to one side. However, the RAD movement was very unstructured: there was no commonly agreed definition of a suitable process and many organisations came up with their own definition and approach. Many major corporations were very interested in the possibilities but they were also concerned that they did not lose the level of quality in the end deliverables that free-flow development could give rise to. The DSDM Consortium was founded in 1994 by an association of vendors and experts in the field of software engineering and was created with the objective of "jointly developing and promoting an independent RAD framework" by combining their best practice experiences. The origins were an event organised by the Butler Group in London. People at that meeting all worked for blue-chip organisations such as British Airways, American Express, Oracle and Logica (other companies such as Data Sciences and Allied Domecq have since been absorbed by other organisations). At the initial meeting it was decided that Jennifer Stapleton, then of Logica, would put together an architecture for an end-to-end, user-centric but quality-controlled method for iterative and incremental development. The resulting architecture was designed to be fully compatible with ISO 9000 and PRINCE2, which were two major concerns for the group. Once the architecture was in place (a month after the initial meeting), the Consortium formed various task groups to populate it with all aspects of software development, including〔project management tools〕 and techniques, quality and testing, development tools and techniques, personnel and software procurement. An oversight group led by the architect and consisting of the chairs of the task groups ensured consistency of the approach as it was developed. Although many of the Consortium members were direct business competitors, they shared freely how they had addressed the various aspects. Best practice was extracted and formed into a cohesive whole. As the Consortium grew in its first year from a handful of organisations to sixty, the content of the method became increasingly robust. Version 1 was baselined in December 1994 and published in February 1995. The result was a generic method covering people, process and tools that was formed from the experiences of organisations of all sectors and sizes. The DSDM Consortium is a not-for-profit, vendor-independent organisation which owns and administers the DSDM framework.〔(【引用サイトリンク】url=http://www.dsdm.org/wp-content/uploads/2013/01/Terms-Conditions-Community-Membership-Jan-2013.pdf )〕 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「dynamic systems development method」の詳細全文を読む スポンサード リンク
|